fix(task): fix closure compatibility issue with ZoneDelegate._updateT… #878
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
|
Joined Google github org |
…askCount onHasTask wasn't getting triggerred for the Angular Zone for setTimeout when the application was closure compiled. This was causing errors with Protractor not being able to wait for a closure compiled application using setTimeout.
|
CLAs look good, thanks! |
1 similar comment
|
CLAs look good, thanks! |
…askCount
onHasTask wasn't getting triggerred for the Angular Zone for setTimeout
when the application was closure compiled. This was causing errors with
Protractor not being able to wait for a closure compiled application using setTimeout.